This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
RE: Problem populating authors fields on docs with no readers fields ~Lily Nonwetherjip 10.Dec.03 05:20 PM a Web browser Applications Development 6.0.1 CF2Windows NT
The issue is that when you delete the authors field, your agent no longer has access to the document.
If your agent is signed by your server ID (the same as the one in the separate authors field), you'll probabbly find it'll work (provided that the authors field contains the full heirarchical name).
But it's never a good idea to hard code names of servers in fields.
Instead, try to have another authors field on the document (maybe call it DocAuthors), and put in the role which you can assign to the server and admin users Eg. '[DocAuthors]', and also assign this to the ID which has saved the agent (the signer, or server in your case).
It's also good practice to include a readers field eg. DocReaders, and put in '[DocReaders]', assigning the role to those that may need it.
This will make sure that the agent and server always has access to the documents, and if they need to process the data, they can. This way you can specify users who will always have access to the documents, and the main authors field (the one you're updating) will take over when users aren't assigned the 'DocAuthors' or 'DocReaders' roles.
Only assign the 'DocReaders' role to users who need to always read all data. Only assign 'DocAuthors' to users who always need to edit all data (eg. admin, servers, and agents). And for the rest of your users don't assign either role - this way the authors field will take precedence - if their name is in the field, they'll be able to read and process the document.
A bit long winded...but let me know if it's not clear. The above is a 'best practice' which will ensure that you never lose control of your data.